Skip to content

chore: remove name_pretty_override (batch 2)#16870

Merged
jskeet merged 2 commits intogoogleapis:mainfrom
jskeet:remove-name-pretty-override-7
Apr 29, 2026
Merged

chore: remove name_pretty_override (batch 2)#16870
jskeet merged 2 commits intogoogleapis:mainfrom
jskeet:remove-name-pretty-override-7

Conversation

@jskeet
Copy link
Copy Markdown
Contributor

@jskeet jskeet commented Apr 29, 2026

This removes the override from Cloud APIs, as far as google-cloud-compute-v1beta.

jskeet added 2 commits April 29, 2026 13:17
This removes the override from Cloud APIs, as far as
google-cloud-compute-v1beta.
@jskeet jskeet requested a review from parthea April 29, 2026 13:59
@jskeet jskeet requested review from a team as code owners April 29, 2026 13:59
@jskeet jskeet requested review from TrevorBergeron and removed request for a team April 29, 2026 13:59
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the naming conventions for several Google Cloud Python client libraries, primarily by removing redundant "API" suffixes and standardizing product names. The review feedback highlights that some of these changes, such as renaming "AppEngine" to "App Engine" and maintaining specific component names for BeyondCorp packages, are necessary for consistency and clarity. Additionally, the renaming of the "common" package to "Common Operation Metadata type" was flagged as overly specific and potentially misleading, with a suggestion to use "Common" instead.

"library_type": "OTHER",
"name": "appenginelogging",
"name_pretty": "App Engine Logging Protos",
"name_pretty": "AppEngine Logging",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The product name is typically spelled with a space: "App Engine". Using "AppEngine" is non-standard for the pretty name.

Suggested change
"name_pretty": "AppEngine Logging",
"name_pretty": "App Engine Logging",

Comment on lines +1 to +2
Python Client for AppEngine Logging
===================================
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The product name should be "App Engine" (with a space).

Suggested change
Python Client for AppEngine Logging
===================================
Python Client for App Engine Logging
====================================

"library_type": "CORE",
"name": "common",
"name_pretty": "Google Cloud Common",
"name_pretty": "Common Operation Metadata type",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Renaming the general "common" package to a specific type name like "Common Operation Metadata type" is misleading. If the goal is to simplify, "Common" or "Google Cloud Common" would be more appropriate.

Suggested change
"name_pretty": "Common Operation Metadata type",
"name_pretty": "Common",

Comment on lines +1 to +2
Python Client for Common Operation Metadata type
================================================
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The title "Common Operation Metadata type" is too specific for the google-cloud-common package. Reverting to a more general name like "Common" is recommended.

Suggested change
Python Client for Common Operation Metadata type
================================================
Python Client for Common
========================

@jskeet jskeet enabled auto-merge (squash) April 29, 2026 15:33
@jskeet jskeet merged commit c053b98 into googleapis:main Apr 29, 2026
30 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants